Systems and methods for clinician control of stimulation system

ABSTRACT

Systems and methods for programming and logging medical device and patient data are provided. The systems include a handheld device, which is capable of communicating with a medical device, and a base station, which provides connectivity for the handheld device to accomplish various functions such as recharging, programming, data back-up and data entry. The methods comprise the steps of detecting a medical device, obtaining and recording information from the medical device. Additionally, medical device parameters may be modified and the recorded information may be archived for future reference.

RELATED APPLICATIONS

This application is a continuation of U.S. patent application Ser. No. 11/541,890, filed Oct. 2, 2006 (now U.S. Pat. No. 7,761,167 issued Jul. 20, 2010), which is: a continuation-in-part of U.S. patent application Ser. No. 11/150,418, filed Jun. 10, 2005 (now U.S. Pat. No. 7,239,918 issued Jul. 3, 2007), which claims the benefit of U.S. Provisional Patent Application Ser. No. 60/599,193, filed Aug. 5, 2004; a continuation-in-part of U.S. patent application Ser. No. 11/149,654, filed Jun. 10, 2005 (now U.S. Pat. No. 7,565,198 issued Jul. 21, 2009), which claims the benefit of U.S. Provisional Patent Application Ser. No. 60/578,742, filed Jun. 10, 2004; a continuation-in-part of U.S. patent application Ser. No. 11/150,535, filed Jun. 10, 2005 (now U.S. Pat. No. 7,813,809 issued on Oct. 12, 2010 published as United States Patent Application No. 20050278000 published on Dec. 15, 2005), which claims the benefit of U.S. Provisional Patent Application Ser. No. 60/680,598, filed May 13, 2005; and a continuation-in-part of U.S. patent application Ser. No. 11/517,056, filed Sep. 7, 2006 (published as United States Patent Application Publication No. 20070060955 published on Mar. 15, 2007), which claims the benefit of U.S. Provisional Patent Application Ser. No. 60/801,003, filed May 17, 2006, all of which are incorporated herein by reference.

BACKGROUND OF THE INVENTION

The invention relates generally to systems and methods for programming, tracking and recording data from electronic devices. More specifically, the present invention relates to systems and methods for programming, tracking and recording data from medical devices, and especially implantable medical devices (IMDs).

Medical devices, specifically IMDs, are commonly used today to treat patients suffering from various ailments, including by way of example, pain, incontinence, movement disorders such as epilepsy, Parkinson's disease, and spasticity. Additional IMD therapies appear promising to treat a variety of other medical conditions, including physiological, psychological, and emotional conditions. As the number of IMD therapies increases, so do the demands placed on these medical devices.

Known IMDs, such as, cardiac pacemakers, tachyarrhythmia control devices, drug delivery devices, and nerve stimulators, provide treatment therapy to various portions of the body. While the present invention may be used with various medical devices, by way of example and illustration, an implantable pulse generator (IPG) device will be discussed to illustrate the advantages of the invention. In the case of providing electrical stimulation to a patient, an IPG is implanted within the body. The IPG is coupled to one or more electrodes to deliver electrical stimulation to select portions of the patient's body. Neuromuscular stimulation (the electrical excitation of nerves and/or muscle to directly elicit the Contraction of muscles) and neuromodulation stimulation (the electrical excitation of nerves, often afferent nerves, to indirectly affect the stability or performance of a physiological system) and brain stimulation (the stimulation of cerebral or other central nervous system tissue) can provide functional and/or therapeutic outcomes.

There exist both external and implantable devices for providing beneficial results in diverse therapeutic and functional restorations indications. The operation of these devices typically includes the use of an electrode placed either on the external surface of the skin, a vaginal or anal electrode, or a surgically implanted electrode. Implantable medical devices may be programmable and/or rechargeable, and the devices may log data, which are representative of the operating characteristics over a length of time. While existing systems and methods provide the capability of programming or recharging IMDs, many limitations and issues still remain.

Implantable devices have provided an improvement in the portability of neurological stimulation devices, but there remains the need for continued improvement in the programming and data management related to such devices. Medical devices are often controlled using microprocessors with resident operating system software. This operating system software may be further broken down into subgroups including system software and application software. The system software controls the operation of the medical device while the application software interacts with the system software to instruct the system software on what actions to take to control the medical device based upon the actual application of the medical device.

As the diverse therapeutic and functional uses of IMDs increase, and become more complex, system software having a versatile interface is needed to play an increasingly important role. This interface allows the system software to remain generally consistent based upon the particular medical device, and allows the application software to vary greatly depending upon the particular application. As long as the application software is written so it can interact with the interface, and in turn the system software, the particular medical device can be used in a wide variety of applications with only changes to application specific software. This allows a platform device to be manufactured in large, more cost effective quantities, with application specific customization occurring at a later time.

While handheld programmers are generally known in the art, there exist many gaps in the methods for programming and tracking specific system or patient data related to medical devices, especially those of the implanted type. Specifically, the art is lacking cohesive systems and methods for programming medical devices, logging medical device and patient data, recharging portable control devices and providing hard copies of information, such as patient or system information.

SUMMARY OF THE INVENTION

Filling the identified needs, the present invention provides systems and methods for programming medical devices, logging medical device and patient data, recharging portable control devices and providing hard copies of information, such as patient or system information.

Generally, the systems comprise a handheld device and a base station. The handheld device provides mobile data management and medical device communications capabilities. The base station provides a connectivity point for the handheld unit, thereby allowing recharge of the handheld unit, printing from the handheld unit, the base station, or the handheld unit while residing in the base station, or data entry or modification, among other functions.

Generally, the methods comprise the steps of detecting a medical device and obtaining and recording information from the medical device. Further, medical device parameters may be altered and information archived for future reference.

The systems and methods of the present invention fill the void in the prior art by providing a convenient means to program medical devices, to log data recorded by, and parameters of, medical devices and the ability to create a hard copy of information, such as recorded device or patient data or system parameters.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is an elevation view of a system according to the present invention in use.

FIG. 2 is a diagrammatic representation of an embodiment of a system according to the present invention.

FIG. 3 is a perspective view of a first embodiment of a handheld device according to the system in FIG. 2.

FIG. 4 is a diagrammatic representation of electrical components used in the handheld device of FIG. 3.

FIG. 5 is a perspective view of a second embodiment of a handheld device according to the system in FIG. 2.

FIG. 6 is a perspective view of a first embodiment of a base station according to the system in FIG. 2.

FIG. 7 is a perspective view of a second embodiment of a base station according to the system in FIG. 2.

FIG. 8 is a perspective view of the first embodiment of a base station having the handheld device of FIG. 3 docked thereto.

FIG. 9 is a perspective view of the system in FIG. 8 and further including an instruction manual.

FIG. 10 is a flow chart of an embodiment of the method of software control for programming and logging device data according to an embodiment of the present invention.

FIG. 11 is an elevation view of a display screen showing the implementation of an embodiment of the method of FIG. 10.

DESCRIPTION OF THE PREFERRED EMBODIMENT

Although the disclosure hereof is detailed and exact to enable those skilled in the art to practice the invention, the physical embodiments herein disclosed merely exemplify the invention which may be embodied in other specific structures. While the preferred embodiment has been described, the details may be changed without departing from the invention, which is defined by the claims.

System

FIG. 1 depicts an embodiment of a system 100 according to the present invention in use. The clinical programmer system 100 comprises generally two subsystems: a mobile, handheld device 101 and a base station 102. The handheld device 101 communicates with a medical device 200, which may be implanted in a patient 202, over a first communication channel 204 and provides an interface to a user, which may be a clinician 206, to enable control of the handheld device 101 and the medical device 200. As stated above, while the present invention may be used with various medical devices 200, by way of example and illustration, an implantable pulse generator (IPG) device will be discussed to illustrate the advantages of the invention.

Referring now to FIG. 2, the embodiment of FIG. 1 is shown diagrammatically. As can further be seen from this figure, the base station 102 may be coupled to the handheld device 101 over a second communication channel 208, thereby allowing performance of various administrative functions, such as battery charging, data back-up, and printing. The base station 102 may have a user input device 103 and a data output device 104. The input device 103 may be, without limitation by way of example, a keyboard, a computer mouse, a digital tablet, a computer network, or the handheld device 101, itself. A plurality of input devices may be used. The data output device 104 may be, without limitation by way of example, a cathode ray tube, a liquid crystal display, a printer, a magnetic disk drive, an optical disk drive, a computer network, or the handheld device 101, itself. A plurality of output devices may be used.

Handheld Device

Referring to FIGS. 2-4, an embodiment of a handheld device 101 according to the present invention is shown. The handheld device 101 is intended to function as a user interface to a medical device 200, such as an IPG, thereby providing sophisticated operation control and intimate access to the programming of the IPG 200 and patient and system data contained therein. Generally, the handheld device 101 comprises a housing 106 that contains a controller 108, associated memory 110 and communications components 112, a telemetry module 114, a power supply 116, external connection hardware 118, and a user interface 130. Optionally, rather than residing in the housing 106, the telemetry module 114 may be a separate component coupled to the device 101. In addition, the handheld device 101 may further comprise recharging circuitry 122, to enable replenishment of the power supply 116. All of the components may be mounted to 1 or more printed circuit boards 124.

In a representative embodiment, the housing 106 is formed from an impact resistant molded plastic and is adapted to fit comfortably into a user's hand. A desirable size for such adaptation may be 25 centimeters long by 8 centimeters wide by 5 centimeters thick; however, the dimensions may change depending upon how the handheld device 101 is used. The housing 106 may include sections having different widths. That is, the housing 106 may have a first section 126 comprising a narrower width for comfortable placement in a user's hand contrasted to a second section 128 comprising a wider width for accommodation of certain features, such as a screen 130 of desirable size. The housing 106 generally houses one or more printed circuit boards 124 carrying electrical components such as a microcontroller 108, nonvolatile memory 110, communications transceivers 112, and associated biasing circuitry. External connections 118 are provided through, or extending from, the housing 106 wherever desired to allow physical connection to other electronic devices. The external connection hardware 118 may include a removable media interface such as Compact Flash memory, a communications interface such as a Universal Serial Bus (USB) interface or conventional serial interface, like an RS-232 interface, or even device support tabs 138 a used in docking the handheld device 101 to the base station 102. Additionally, user interface mechanisms may be accessible through the housing 106. For instance, a reset button 107 may be available by use of a special tool, such as a stylus 109. Also, it is contemplated that a power button 111 provides user access through the housing 106 to command system power.

The microcontroller 108 in the handheld device 101 is responsible for running system software, as well as application software. While these tasks may be divided amongst multiple controllers, a single controller 118 is desirable. Representative system software is Microsoft Corporation's Windows CE®. Additional system software features, such as peripheral interfaces, are optional and dependent on the software approach used. Associated with the microcontroller 108 is some sort of electronic memory 110. A desirable memory 110 includes nonvolatile random access memory. Nonvolatile memory provides insurance against loss of data in a situation where power is lost and facilitates an extremely low power or zero power inactive (sleep) state of the microcontroller 108. The nonvolatile memory element 110 is capable of storing patient records, arranged by visit or other desirable characteristics, so that a clinician using the handheld device 101 can quickly establish a historical perspective on patient treatment. The nonvolatile memory element 110 may also store all or part of operating system software, application software, or data for the general use of the microcontroller 108.

The device 101 also has a communications module 114 for communicating with the IPG 200 or other medical device. The communications module 114 may be a telemetry module, which is a protocol translator and radio frequency modem that accepts packets from the microcontroller 108 and converts it into wireless messages directed to the IPG 200. The telemetry module 114 is capable of communicating with individual medical devices 200 within its immediate range and desirably up to six feet away. The telemetry module 114 may implement a variety of communication protocols, such as those standard in the art, or custom communication protocols, which may be predetermined by the capabilities of the medical device 200 to which communications must be sent. The communications module 114 may be disabled while the handheld device 101 is docked on the base station 102.

The device 101 further includes a power supply 116, which provides the required electrical power for desired electronic circuit operation. In one embodiment, a primary power supply 116 may be a rechargeable lithium ion battery. Lithium ion batteries are capable of providing many hours of operation without having to be docked to recharge. For instance, it may be desirable to provide a power supply 115 capable of providing eight hours of use without the need for recharge. While the specific functionality of the device 101 during runtime will affect battery requirements, an acceptable power supply 116 may be a rechargeable lithium ion battery having a capacity of 2600 milliamp hours. The device 101 may also have a backup battery 116′ capable of maintaining program or data memory in the event of a deep discharge or replacement of the primary battery 116. If a rechargeable power supply 116 is used, proper recharging circuitry 122 may be included in the system 100. Such circuitry 122 may be contained within the handheld device 101, as shown, or may reside in the base station 102.

External connection hardware 118 is also provided on the handheld device 101, thereby providing additional input/output capability. Providing data input/output capability, the device may have at least one universal serial bus (USB) port and/or serial communications port, and other ports as needed to communicate with an externally located telemetry module 114 and the base station 102. Also, external connections 118 may be provided to allow the controller 108 of the handheld device 101 to control the base station 102 operation, for example printer operations, in addition to controlling the handheld device 101.

The device 101 further provides a user interface to the IPG 200, so that a clinician can change control parameters in and view data from the IPG 200. In this manner, a clinician may configure parameters in the individual IPG 200 that adjust application limits for a patient user interface to the IPG 200. A patient user interface provides a limited range of programmability for a medical device. For example, a simple patient user interface may be a device having a single button to turn an IMD on or off. In one embodiment, the clinician user interface is a pressure sensitive touch screen 130 incorporated into the handheld device 101. The device 101 may be controlled by use of the stylus 109 on the screen 130. The screen 130 may be a color display screen supporting a fixed or variable pixel resolution. A desirable pixel resolution may be at least 240×240. The embedded operating system software and screen 130 may support both vertical and horizontal viewing.

The handheld device 101 further may implement a system of checks, balances, and redundancies to qualify and prevent the use of unsafe combinations of settings.

FIG. 5 shows a second embodiment of handheld device 101 according to the present invention where, in addition to or instead of the touch screen 130, the housing 106 may be provided with an on-board keypad 129 and programmable function keys 131 as means of data entry and device control. Programmable function keys 131, as generally understood in the art, may be physical buttons or specific pixel array on the display 130, the functionality of which is not dedicated but rather may change, depending upon the state of the software. Further, the device 101 may include one or more indicators 127, which signal predetermined conditions to a user.

Generally, two approaches may be desirable for implementation of the handheld device 101. The first approach entails modification and adaptation of an off-the-shelf personal digital assistant (PDA) or other portable computer. If adopted, the first approach may require further encasing the PDA in the housing 106 along with a communications module 114 or providing connectivity for such communications module 114 to the PDA. The second approach may encapsulate a customized printed circuit board 124 and component combination in a customized housing 106. This second approach provides more design flexibility than the first approach and allows tighter control over system components. Whichever approach is desirable, the handheld device 101 may function as a single purpose device. That is, the handheld device 101 may serve only in the system 100, rather than provide general purpose computing functionality.

Base Station

Referring now to FIGS. 2, 6 and 7, an embodiment of a base station 102 according to the present invention is shown. The base station 102 comprises a base station housing 132, a cradle 134 for holding the handheld device 101, and electronic memory 136. Furthermore, the base station 102 may comprise connectivity for other user input devices 103 and a data output device 104. Alternatively, the base station 102 may contain a user input device 103 and a user output device 104. Each component is described in greater detail below.

The base station housing 132 is of any desirable shape. Adaptation may provide stability on a relatively horizontal surface, such as a desk, or on a relatively vertical surface, such as a wall. The housing 132 generally provides a protective cover for desirable electrical components. Desirable components may be those required to carry out functions such as data backup and restore for the handheld device 101, printing of reports or records for affixing hard copies of information to a patient's chart, power recharging of the handheld device 101, entry of patient data, and export and import of data.

The cradle 134 provides a docking point for the handheld device 101. While connectivity to the handheld device 101 could be provided generally anywhere proximate the base station 102, connectors 140 for power and communication to the handheld device 101 may be provided in the cradle 134.

A user input device 103 may be present in the form of a user interface 142, which allows user intervention and control of the base station 102 functionality. While depicted as discrete buttons 142 on the base station 102, user input may also be achieved through the use of any combination of a standard QWERTY computer keyboard, a computer mouse, or even a custom keyboard. If the microcontroller in the handheld device 101 provides, in addition to control of the handheld device 101, system control for the base station 102, a keyboard 143 may serve as the user input device 103 through the base station 102 to the handheld device 101 through the cradle 134. Furthermore, rather than provide a distinct user input device 103 on or connected to the base station 102, the handheld device 101, itself, may serve as the user input device 103. When the handheld device 101 is docked in the base station 102, the visual display 130 on the handheld device 101 may serve as the user input device 103 to access the base station 102 and any output device 104 connected thereto. As depicted in FIG. 5, the handheld device 101 may also have an on-board keyboard 129 that can be used for data entry. User input to the base station 102 may also be entered through the handheld device screen 130 by way of a stylus 109. It may be desirable to provide storage 139 of the stylus somewhere on the base station 102 or on the handheld device 101 so that it is easily accessible to the user. Positioning of the cradle 134 in the base station 102 may be determined on a basis of ergonomic considerations such as reach and viewing angle.

The base station 102 also includes, or provides connectivity for, a data output device 104. The data output device 104 may comprise a printer 144 to provide hard copy documentation on paper 146 or other substrate suitable for placing into a patient's medical chart. A suitable printer 144 may be a four inch label printer, such as an OEM kiosk printer, that may be mounted on or in the base station 102. Rather than have the printer 144 mounted to the base station 102, a data output device 104 may be connectable to the base station 102. Connectivity of the base station 102 to external devices may be achieved in any desirable way, such as through the use of ports 145. Ports 145 that may be desirable are USB connections or a digital video connection if the output device 104 is a computer monitor 147. A computer monitor 147 may provide an enhanced visual display for the user. The specific technology of the output device 104 is not important; however, if a printer 144 is used, it may employ a thermal print element, inkjet or even impact/ribbon technology.

Data backup may be achieved through the use of computer readable electronic memory 136. The memory 136 may be of any desirable type, including by way of example nonvolatile random access memory, magnetic data storage, optical data storage, or media such as so called flash drives, or other memory types not yet invented.

FIG. 8 depicts an embodiment of a system 100 according to the present invention comprising a base station 102 shown with a handheld device 101 docked thereto. The position of the cradle 134 is not critical, and the handheld device 101 may rest in the cradle 134 in such a way that the device is positioned conveniently for user viewing, keypad-screen control and data input. A docking support 138 b may also be provided, to receive the device support tabs 138 a to keep the device 101 in place when docked in the base station 102. If positioning of the screen 130 is a different orientation while in the cradle 134 as opposed to when the device 101 is used outside of the cradle 134, the device support tabs 138 a may physically contact the docking support 138 b and signal to the handheld device software that the orientation of the image on the display 130 needs to be altered. The LCD screen 130 may function both as a user input device 103 to the base station 102 and as a data output device 104 from the base station 102. The cradle 134 may also have an adjustable viewing angle. As elaborated below, the system 100 may be provided with accompanying documentation 150, as shown in FIG. 9.

Software

In addition to physical systems, the present invention contemplates methods of establishing a communication link with a medical device, retrieving medical device data, programming the medical device, logging medical device data or parameters, and archiving information. Additionally, prior to establishing a communication link with a medical device, the method may include the steps of determining whether any medical devices are within a scannable range and selecting a medical device with which to establish the communications link. Archiving information may include recording data on a variety of media, such as recording on computer readable media or printing on paper. Some or all of the steps can occur automatically by way of software, initiated by an event such as inserting the handheld computer into the base station, or by human intervention in conjunction with the software. An embodiment 500 of a user interactive method is shown in FIG. 10. As shown, the steps are carried out by application software, but are generally initiated by a user of the handheld device 101.

In a representative embodiment, the application software included on the handheld device provides the full range of the clinician experience—from initial patient engagement to documentation and retrieval of patient visits. Although the software may exist in any programming language adaptable to the specific microcontroller, C# (C sharp) is preferred due to its tendency towards rapid development, its C-like syntax, its object orientation, and the high degree of reliability of developed applications. The application software may run on top of the system software that is loaded into the handheld device 101.

The application software interfaces with a database 501. The database 501, which encodes patient names, visits, and other data, may be implemented using Microsoft® structured query language (SQL) mobile Edition having desirable data backup and restore features. Regardless of the type of database 501, a database interface may be installed on the handheld device 101 as part of the application software install. The database interface allows a user to access patient data from the database 501. Access to patient data may be achieved by entering patient-identifying information. Such data may consist only of patient contact information or may include complex historical patient data and time stamped medical device data. The database 501 containing comprehensive patient information may reside on the handheld device 101 directly. Alternatively, the database 501 may reside on the base station 102 or a hospital computer network. If the database 501 does not reside on the handheld device 101, a temporary data construct containing data fields similar to those in the database 501 is preferred, which allows storage of data for several, but not necessarily all, patients on the handheld device 101.

The database 501 may include several tables. One embodiment may implement two tables: a Patient Table 502, and Visit Table 503. The Patient Table 502 contains all patient information that is relatively constant. The purpose of the Visit Table 503 is to record and store relevant IPG data that would be collected over a series of visits. The user may then display trend or comparative data in graphical formats. Fields of data in the respective tables 502,503 may be hard coded, or reconfiguration of the tables 502,503 may be allowed.

FIG. 10 also shows a navigational relationship of a plurality of displayed application software screens. The number of application screens is not determinative of the present invention. In one embodiment, four main application screens 504 are used: a primary programming and administrative screen 506, an advanced programming screen 508, a patient history screen 510, and a tools screen 512. Users may also add customizable screens as needed for other applications A plurality of screen selectors is displayed on the screen 130 to enable a user to switch the image on the display screen 130 to a different application software screen. That is, on the display screen 130 of the handheld device 101, where an application screen is displayed, a plurality of screen selectors may be provided on the border of the functional screen. As shown in FIGS. 10 and 11, a representative embodiment of the screen selectors is a series of selectable tabs 514. Generally, tabbed screen navigation is well-known in the art. When the desired screen selector 514 is chosen, the appropriate application screen is displayed on the handheld device screen 130. The tab control 407 methodology allows for faster screen loading and more visible navigational choices. User interface functionality on the various screens may be predetermined and remain relatively static, or the functions included on the particular screens may change depending upon frequency of use or other desired operating characteristics. For ease of description, a relatively static implementation is described.

Referring again to FIG. 10, when the handheld device is powered on, a logon screen 516 is displayed. The software may be under revision control and the revision level may be displayed on the logon screen 516. To proceed past the logon screen 516, a user may be prompted to verify that he or she has authority to do so. Due to the sensitive nature of medical information, to enhance patient privacy, and perhaps to comply with appropriate privacy guidelines, the system may control access to its data and functions through a protection scheme. The protection scheme may be a relatively simple text password implemented in software, or a more complicated scheme of data protection involving such things as biometric measurements may be employed. Upon authentication, the user is taken to the primary application screen 506.

The primary screen 506 is displayed to a user after user authentication has occurred. The primary screen 506 may group a predetermined number of the most commonly used functions in the system onto a single screen 506. The primary screen 506 provides access to existing patient selection 518, new patient data entry 520 and editing of database records 522. Access to various administrative functions may also be provided via the primary screen 506. To switch between main application screens 504, the tab control 514 is used.

The advanced programming screen 508 provides a user interface to the data and parameters 524 contained in the medical device 200. Examples of medical device data 524 may be an indication of remaining battery charge in the medical device 200, recharge time, and stimulation time. While programmable parameters 524 for various medical devices 200 will differ, representative parameters 524 for an IPG are pulse amplitude, pulse duration and pulse frequency and sequence timing. Additionally, the device interface screen 508 may allow the selection or alteration of limits for any user (patient) adjustable parameters. Furthermore, a set of predetermined parameters or collections of parameters based on common electrophysiological behavior may be preloaded to minimize the effort on the part of the user. Also, after recognizing programmed parameters, the handheld device 101 may recommend parameters to the user.

The patient history screen 510, allows access to existing patient data 526 drawn from the database 501 and entry of new patient visit information, including textual diary data. Once the patient data 526 has been configured, the patient may automatically be identified during his or her next session and relevant historical data may be made available during subsequent patient visits. Rather than automatic identification, the device 101 may be programmed with the proper communications information or a clinician may query a range of medical device identifiers. During a session with a patient, the software may notify the clinician if communications 204 is interrupted or another medical device 200 intrudes on the session. To avoid the potential for incorrectly or incompletely communicating with medical devices, the communications protocol between the handheld device and any medical device may include the identification of which medical device is being addressed by way of, for example, a unique electronic signature or device serial number.

A tools screen 512 is provided to enable modification of system parameters such as accessibility passwords and date and time functions. Also, the tools screen 512 may provide access to the database 501 as well as base station 102 functionality such as printing. Further, the tools screen 512 may provide medical device query capability, thus allowing the device 101 to scan a predetermined area for responsive medical devices 200.

A customizable screen, or plurality of customizable screens, may also be desired, the functionality of which can be tailored to a specific user's operating procedures or tailored applications. Alternatively, the customizable screen may be a screen that is available only when the handheld device 101 is docked in a base station 102.

Some functionality may be desirable no matter which screen is displayed. That is, the application software may monitor the occurrence of hardware faults and also monitor battery level. When predetermined events occur, the handheld device 101 may emit a warning, such as a visual or audio warning, when a hardware fault occurs or if the battery charge for either the telemetry module 114 or handheld device 101 is at a predetermined level. Also, an extensive help menu system may be incorporated. The help menu may be accessible from any displayed screen, perhaps as a separate tab control 514.

Although the handheld device 101 application software provides the ability to download patient data from a database 501, a clinician may have the option of using the handheld device 101 without having patient data available. That is, if all patient data is erased off the handheld device 101 or otherwise not entered, the device 101 may still function as a user interface to the medical device 200. This may require the user to enter at least a default set of patient data, such as patient last name or medical device code.

System Use

The system 100 may be constructed for safe operation within an operating room and desirably does not interfere with any hospital electronic equipment. While it is generally expected that only the handheld device 101 will be used in the operating room, a base station 102 may also be located in an operating room. When the handheld device 101 is used in an operating room or other location where sterility is of utmost importance, the device 101 can be sterilized, or a sterile device cover may be provided to enclose or shield the device 101.

A clinician can use the handheld device 101 in an operating room to turn on an IPG 200 and adjust stimulus parameters in the IPG 200. The clinician simply enters predetermined patient data to be associated with the IPG 200 that is in the process of being programmed. The clinician who is using the handheld device 101 may be the surgeon who has placed the IPG 200, a physician's assistant, a nurse, or other clinician authorized to do so. It is to be appreciated that the handheld device 101, through a wireless range, may be used outside of the sterile field.

In addition to use in an operating room, a clinician may use the system 100 in an office setting when a patient returns for follow-up visits. The handheld device 101 allows a clinician to interrogate the IPG 200 for compliance data such as recharge history and current stimulus parameter settings. The clinician may make adjustments to the stimulus parameters as necessary based on the feedback from the patient. The clinician may also schedule upcoming appointments in the handheld device 101 and recall any details of past appointments.

To ensure reliable and robust operation, the system, at least while certain software is active, may be a single purpose device. Although not a required feature, the system may have the ability to connect to a hospital computer network or directly interface to other devices such as an external disk drive 148, as shown in FIG. 7. The disk drive 148 may comprise a hard magnetic disk drive or a drive capable of reading or writing removable media, such as magnetic or optical disks or non-volatile semiconductor memory cards or sticks. As shown in FIG. 9, the system 100 may be provided with all appropriate documentation 150 that conforms to relevant guidelines and further conforms to health and safety requirements as defined by the appropriate regulatory bodies. In addition to complying with guidelines mandated by regulatory bodies, the documentation 150 may include printed or computer readable instructions 150, which provide guidance on such things as the use of the system, data recovery techniques, and elaborate on the features provided. The features may be general to a system according to the present invention or predetermined custom features may be described in detail.

The foregoing is considered as illustrative only of the principles of the invention. Furthermore, since numerous modifications and changes will readily occur to those skilled in the art, it is not desired to limit the invention to the exact construction and operation shown and described. While the preferred embodiment has been described, the details may be changed without departing from the invention, which is defined by the claims. 

We claim:
 1. A method comprising: establishing a first communications link between a handheld electronic device and an implantable medical device; establishing a second communications link between the handheld electronic device and a base station, wherein the handheld electronic device includes a user interface configured to serve as a user input device of the base station when the handheld electronic device is docked to the base station; providing access to the base station and an output device connected to the base station via the user interface of the handheld electronic device when the handheld electronic device is docked to the base station; and controlling both the handheld device and the base station via the user interface of the handheld electronic device, wherein the user interface of the handheld electronic device comprises a display screen that further functions as a data output device from the base station.
 2. The method of claim 1, wherein the implantable medical device is configured to deliver a therapy.
 3. The method of claim 2, wherein the implantable medical device comprises an implantable pulse generator.
 4. The method of claim 1, further comprising: communicating with the implantable medical device; obtaining information from the implantable medical device; and recording the obtained information.
 5. The method of claim 4, wherein at least a portion of the obtained information comprises therapy information stored in the implantable medical device.
 6. The method of claim 4, further comprising locating, in a database, patient information based on the obtained information.
 7. The method of claim 6, wherein the database resides in the base station.
 8. A non-transitory computer-readable medium comprising instructions that, upon execution, cause a processor to: establish a first communications link between a handheld electronic device and an implantable medical device; establish a second communications link between the handheld electronic device and a base station, wherein the handheld electronic device includes a user interface configured to serve as a user input device of the base station when the handheld electronic device is docked to the base station; provide access to the base station and an output device connected to the base station via the user interface of the handheld electronic device when the handheld electronic device is docked to the base station; and control both the handheld device and the base station via the user interface of the handheld electronic device, wherein the user interface of the handheld electronic device comprises a display screen that further functions as a data output device from the base station.
 9. The non-transitory computer-readable medium of claim 8, wherein the implantable medical device is configured to deliver a therapy.
 10. The non-transitory computer-readable medium of claim 9, wherein the implantable medical device comprises an implantable pulse generator.
 11. The non-transitory computer-readable medium of claim 8, further comprising instructions that cause the processor to: communicate with the implantable medical device; obtain information from the implantable medical device; and record the obtained information.
 12. The non-transitory computer-readable medium of claim 11, wherein at least a portion of the obtained information comprises therapy information stored in the implantable medical device.
 13. The non-transitory computer-readable medium of claim 11, further comprising instructions that cause the processor to locate, in a database, patient information based on the obtained information.
 14. The non-transitory computer-readable medium of claim 13, wherein the database resides in the base station.
 15. A handheld electronic device comprising: means for establishing a first communications link between the handheld electronic device and an implantable medical device; means for establishing a second communications link between the handheld electronic device and a base station, wherein the handheld electronic device includes a user interface configured to serve as a user input device of the base station when the handheld electronic device is docked to the base station; means for providing access to the base station and an output device connected to the base station via the user interface of the handheld electronic device when the handheld electronic device is docked to the base station; and means for controlling both the handheld device and the base station via the user interface of the handheld electronic device, wherein the user interface of the handheld electronic device comprises a display screen that further functions as a data output device from the base station.
 16. The device of claim 15, wherein the implantable medical device is configured to deliver a therapy.
 17. The device of claim 16, wherein the implantable medical device comprises an implantable pulse generator.
 18. The device of claim 15, further comprising: means for communicating with the implantable medical device; means for obtaining information from the implantable medical device; and means for recording the obtained information.
 19. The device of claim 18, wherein at least a portion of the obtained information comprises therapy information stored in the implantable medical device.
 20. The device of claim 18, further comprising means for locating, in a database, patient information based on the obtained information.
 21. The method of claim 20, wherein the database resides in the base station. 